-- card: 3703 from stack: in
-- bmap block id: 0
-- flags: 0000
-- background id: 2619
-- name: CUSTOM FONTS


-- part 1 (field)
-- low flags: 01
-- high flags: 0001
-- rect: left=37 top=42 right=91 bottom=475
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 1
-- font id: 3
-- text size: 12
-- style flags: 8448
-- line height: 16
-- part name: 


-- part contents for card part 1
----- text -----
Commands and Structures to Avoid

CUSTOM FONTS

-- part contents for background part 2
----- text -----

If your stack makes use of custom fonts, you must not include them in the stack itself.  This version of HyperDA, is unable to look within a document (which, from HyperDA’s perspective, is what a stack is) for fonts.  Future releases of HyperDA will be able to handle this task.  At the moment, HyperDA can only access fonts  stored in the System resource.  If your stack requires custom fonts to work properly, you should:

1.Supply them as a separate font file on the disk.

2.Instruct your users to install the fonts in their Systems.